home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01b.txt
/
000078_icon-group-sender_Tue Jul 3 13:37:30 2001.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id f63KY0s05063
for icon-group-addresses; Tue, 3 Jul 2001 13:34:00 -0700 (MST)
Message-Id: <200107032034.f63KY0s05063@baskerville.CS.Arizona.EDU>
From: Art Eschenlauer <art.eschenlauer@sufsys.com>
To: "'icon-group@CS.Arizona.EDU'" <icon-group@cs.arizona.edu>
Subject: Software testing for Icon?
Date: Mon, 25 Jun 2001 11:33:50 -0500
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 718
One concern that I expect people to raise with respect to using Icon in the
"mainstream" is, "Icon cannot be trusted because it does not typecheck
arguments at compile time. How can you protect against programmer errors in
the arguments passed during infrequently-executed invocations?" I don't
think that the response (however true) that C++ has compile-time
type-checking and yet still is notorious for null pointer errors, etc, will
convince anybody.
This raises two questions in my mind regarding Icon:
1. Should one adopt a "defensive programming style", always checking the
arguments passed to each routine?
2. What work has been done on developing rigorous software-testing
methodology for Icon programs?